Communication device for providing an automatically initiated outgoing communication as an incoming communication

ABSTRACT

A communication device and method for providing an automatically initiated outgoing communication as an incoming communication are provided. Outgoing communication is automatically initiated via a communication interface of the communication device. After the outgoing communication is initiated, an indication of the outgoing communication is provided at the communication device, such that the outgoing communication is provided as an incoming communication at the communication device.

CROSS-REFERENCE TO RELATED APPLICATION

The instant application is a continuation application of U.S. patentapplication Ser. No. 13/397,454, filed Feb. 15, 2012, the disclosure ofwhich is incorporated herein by reference.

FIELD

The specification relates generally to communication devices, andspecifically to a communication device for providing an automaticallyinitiated outgoing communication as an incoming communication.

BACKGROUND

The evolution of computers is currently quite active in the mobiledevice environment. It is now well-known to including calendaring,contacts, and messaging functions in mobile devices. More recently,there has been a veritable explosion of the number and type ofapplications that are configured to the unique form factors andcomputing environments of mobile devices.

BRIEF DESCRIPTIONS OF THE DRAWINGS

For a better understanding of the various implementations describedherein and to show more clearly how they may be carried into effect,reference will now be made, by way of example only, to the accompanyingdrawings in which:

FIG. 1 depicts a system for providing an automatically initiatedoutgoing communication as an incoming communication, according tonon-limiting implementations.

FIG. 2 depicts a template for providing an indication of an incomingcommunication in the system of FIG. 1, according to non-limitingimplementations.

FIG. 3 depicts a method for providing an automatically initiatedoutgoing communication as an incoming communication, according tonon-limiting implementations.

FIG. 4 depicts the system of FIG. 1 with an outgoing communicationautomatically initiated, according to non-limiting implementations.

FIG. 5 depicts the system of FIG. 1 with the template of FIG. 2populated using meeting data, according to non-limiting implementations.

FIG. 6 depicts an indication of an outgoing communication provided as anincoming communication, according to non-limiting implementations.

DETAILED DESCRIPTION

An aspect of the specification provides a communication devicecomprising: a processor and a communication interface, the processorenabled to: automatically initiate an outgoing communication at ascheduled given time via the communication interface; and, after theoutgoing communication is initiated, provide an indication of theoutgoing communication, such that the outgoing communication is providedas an incoming communication.

The outgoing communication can be initiated without providing anindicator of the outgoing communication. The outgoing communication canbe initiated without providing an indicator of the outgoingcommunication other than an indicator of the outgoing communicationrendered in an indicator area of a display of the communication device.The indicator can comprise one or more of an icon and a radio-in-useicon. The indicator area can comprise a header of at the display.

When the outgoing communication is initiated, at least a portion ofnormally provided indications associated with outgoing communicationscan be suppressed. One or more of a dial-out indication and a dial-tonecan be suppressed. At least a portion of normally provided indicationsof outgoing communications can be suppressed by muting a speaker at thecommunication device. At least a portion of normally providedindications of outgoing communications can be suppressed by preventingrendering of an identifier of a remote communication device associatedwith the outgoing communication.

The indication of the outgoing communication can be provided as one ormore of a caller ID (identification), an identifier of the outgoingcommunication, an identifier of a conference call associated with theoutgoing communication, and an identifier of meeting data associatedwith the outgoing communication.

The indication can comprise an incoming communication template withfields populated with outgoing communication data.

The processor can be further enabled to determine that the outgoingcommunication is scheduled by processing a calendar database todetermine that the outgoing communication is associated with meetingdata associated with the scheduled given time.

The processor can be further enabled to automatically initiate theoutgoing communication at one or more of the scheduled given time andwithin a given time period before the scheduled given time.

The processor can be further enabled to automatically initiate theoutgoing communication by: initiating the outgoing communication; and,when a called communication device responds to a request for initiatingthe outgoing communication, automatically providing log-in data forjoining a conference call to the called communication device.

The processor can be further enabled to, when connecting the outgoingcommunication is unsuccessful, automatically reattempt to automaticallyinitiate the outgoing communication after a given time period.

The processor can be further enabled to provide the indication of theoutgoing communication when one of a called communication device answersthe outgoing communication, and when the outgoing communication islogged into an associated conference call.

The processor can be further enabled to, when the indication is providedbefore one of a called communication device answers the outgoingcommunication and the outgoing communication is logged into anassociated conference call, mute the outgoing communication.

A further aspect of the specification provides a method comprising:automatically initiating, at a processor of a communication device, anoutgoing communication at a scheduled given time via a communicationinterface of the communication device; and, after the outgoingcommunication is initiated, providing an indication of the outgoingcommunication at the communication device, such that the outgoingcommunication is provided as an incoming communication at thecommunication device.

The outgoing communication can be initiated without providing anindicator of the outgoing communication. The outgoing communication canbe initiated without providing an indicator of the outgoingcommunication other than an indicator of the outgoing communicationrendered in an indicator area of a display of the communication device.The indicator can comprise one or more of an icon and a radio-in-useicon. The indicator area can comprise a header of at the display.

When the outgoing communication is initiated, at least a portion ofnormally provided indications associated with outgoing communicationscan be suppressed. One or more of a dial-out indication and a dial-tonecan be suppressed. At least a portion of normally provided indicationsof outgoing communications can be suppressed by muting a speaker at thecommunication device. At least a portion of normally providedindications of outgoing communications can be suppressed by preventingrendering of an identifier of a remote communication device associatedwith the outgoing communication.

The indication of the outgoing communication can be provided as one ormore of a caller ID (identification), an identifier of the outgoingcommunication, an identifier of a conference call associated with theoutgoing communication, and an identifier of meeting data associatedwith the outgoing communication.

The indication can comprise an incoming communication template withfields populated with outgoing communication data.

The method can further comprise determining that the outgoingcommunication is scheduled can by processing a calendar database todetermine that the outgoing communication is associated with meetingdata associated with the scheduled given time.

The outgoing communication can be automatically initiated at one or moreof the scheduled given time and within a given time period before thescheduled given time.

Automatically initiating the outgoing communication can comprise:initiating the outgoing communication; and, when a called communicationdevice responds to a request for initiating the outgoing communication,automatically providing log-in data for joining a conference call to thecalled communication device.

The method can further comprise, when connecting the outgoingcommunication is unsuccessful, automatically reattempting automaticallyinitiating the outgoing communication after a given time period.

The indication of the outgoing communication can be provided when one ofa called communication device answers the outgoing communication, andwhen the outgoing communication is logged into an associated conferencecall.

When the indication is provided before one of a called communicationdevice answers the outgoing communication and the outgoing communicationis logged into an associated conference call, the outgoing communicationcan be muted.

Yet another aspect of the specification provides a computer programproduct, comprising a computer usable medium having a computer readableprogram code adapted to be execute a method comprising: automaticallyinitiating, at a processor of a communication device, an outgoingcommunication at a scheduled given time via a communication interface ofthe communication device; and, after the outgoing communication isinitiated, providing an indication of the outgoing communication at thecommunication device, such that the outgoing communication is providedas an incoming communication at the communication device. The computerprogram product can comprise a non-transitory computer program product.

FIG. 1 depicts a system 100 for automatically providing an automaticallyinitiated outgoing communication as an incoming communication, andaccording to non-limiting implementations. System 100 comprises acommunication device 101 enabled to initiate outgoing communications toa remote communication device 103 via a link 106. Communication device101 and communication device 103 will also be respectfully referred tohereafter as device 101 and device 103. This convention will be usedelsewhere in the present specification. Device 103 is further enabled toreceive requests for communications from other communication devices105-1, 105-2 via links 108-1, 108-2, which will also be referred tohereafter generically as a link 108, and collectively as links 108. Thisconvention will also be used elsewhere in the present specification. Forexample, device 103 can comprise a conference call server enabled toreceive communications from one or more of devices 101, 105 in aconference call. In such implementations, communications can comprisetelephone calls, voice calls, mobile calls, VoIP (voice over internetprotocol) calls, PSTN (public switched telephone network) and the like.

As will be described below, device 101 is generally enabled to:automatically initiate an outgoing communication at a scheduled time;and, after the outgoing communication is initiated, providing anindication of the outgoing communication at device 101 as an incomingcommunication at the device 101.

It is further more appreciated that while only three devices 101, 105are depicted in FIG. 1, system 100 can comprise any suitable number ofcommunication devices, including hundreds to thousands to millions ofdevices. Indeed, system 100 can comprise any number of devices enabledto participate in a conference call at device 103.

Furthermore, while only one device 103 is depicted in FIG. 1, system 100can comprise any suitable number of conference call servers.

Device 101 can be any type of electronic device that can be used in aself-contained manner to interact with a communications network via link106. It is hence appreciated that device 101 comprises any suitablecommunication device for communicating with device 103 and/or devices105. Device 101 includes, but is not limited to, any suitablecombination of computing devices, personal computers, laptop computers,portable electronic devices, mobile computing device, portable computingdevices, tablet computing devices, laptop computing devices, desktopphones, telephones, PDAs (personal digital assistants), cellphones,smartphones and the like. Other suitable communication devices arewithin the scope of present implementations.

Each of links 106, 108 comprises any suitable link, including anysuitable combination of wired and/or wireless links, wired and/orwireless devices and/or wired and/or wireless networks, including butnot limited to any suitable combination of USB (universal serial bus)cables, serial cables, wireless links, cell-phone links, cellularnetwork links (including but not limited to 2G, 2.5G, 3G, 4G+, and thelike) wireless data, Bluetooth links, NFC (near field communication)links, WiFi links, WiMax links, packet based links, the Internet, analognetworks, the PSTN (public switched telephone network), access points,and the like, and/or a combination.

It is appreciated that FIG. 1 further depicts a schematic diagram ofdevice 101 according to non-limiting implementations. It should beemphasized that the structure of device 101 in FIG. 1 is purelyexemplary, and contemplates a device that can be used for both wirelessvoice (e.g. telephony) and wireless data communications (e.g. email, webbrowsing, text, and the like). Device 101 comprises at least one inputdevice 200 generally enabled to receive input data, and can comprise anysuitable combination of input devices, including but not limited to akeyboard, a keypad, a pointing device, a mouse, a track wheel, atrackball, a touchpad, a touch screen and the like. Other suitable inputdevices are within the scope of present implementations.

Input from input device 200 is received at processor 208 (which can beimplemented as a plurality of processors, including but not limited toone or more central processing units (CPUs)). Processor 208 isconfigured to communicate with a non-volatile storage unit 212 (e.g.Erasable Electronic Programmable Read Only Memory (“EEPROM”), FlashMemory) and a volatile storage unit 216 (e.g. random access memory(“RAM”)). Programming instructions that implement the functionalteachings of device 101 as described herein are typically maintained,persistently, in non-volatile storage unit 212 and used by processor 208which makes appropriate utilization of volatile storage 216 during theexecution of such programming instructions. Those skilled in the artwill now recognize that non-volatile storage unit 212 and volatilestorage 216 are examples of computer readable media that can storeprogramming instructions executable on processor 208. Furthermore,non-volatile storage unit 212 and volatile storage 216 are also examplesof memory units and/or memory modules.

Processor 208 in turn can also be configured to communicate with adisplay 224, a microphone 226 and a speaker 229. Display 224 comprisesany suitable one of or combination of CRT (cathode ray tube) and/or flatpanel displays (e.g. LCD (liquid crystal display), plasma, OLED (organiclight emitting diode), capacitive or resistive touchscreens, and thelike). It is generally appreciated that display 224 comprises circuitry230 that can be controlled, for example by processor 208, to render arepresentation 232 of data at display 224, for example an indication ofan outgoing communication as explained in further detail below withregard to FIG. 6.

Microphone 226 comprises any suitable microphone for emitting sounddata, which can be transmitted to device 101. Speaker 229 comprises anysuitable speaker for providing sound data at device 101. It isappreciated that microphone 226 and speaker 229 can be used incombination at device 101 to conduct communications comprising a voicecall, for example with one or more of devices 103, 105.

In some implementations, input device 200 and display 224 are externalto device 101, with processor 208 in communication with each of inputdevice 200 and display 224 via a suitable connection and/or link.Similarly, microphone 226 and speaker 229 can be external to device 101,for example integrated into a headset that can be connected to device101.

Processor 208 also connects to a network communication interface 228,referred to hereafter as interface 228, which can be implemented as oneor more radios configured to communicate over link 106. In general, itwill be understood that interface 228 is configured to correspond withthe network architecture that is used to implement link 106. In otherimplementations a plurality of links with different protocols can beemployed and thus interface 228 can comprise a plurality of interfacesto support each link.

While not depicted, in some implementations, device 101 can furthercomprise at least one optional notification device, such as a light, anLED (light emitting diode), a vibrational motor and the like, forproviding notifications of incoming communications, such as phone calls,text messages, emails and the like, either alone or in combination witheach other and/or display 224 and/or speaker 229. Otherwise,notifications of incoming communications are provided via display 224,speaker 229 and/or a combination.

In particular, it is appreciated that non-volatile storage 212 stores anapplication 250 for managing communications. When processor 208processes application 250, processor 208 is enabled to: automaticallyinitiate an outgoing communication at a scheduled time, for example avoice call to device 103; and, after the outgoing communication isinitiated, providing an indication of the communication at device 101 asan incoming communication at the device 101.

In some implementations, non-volatile storage 212 further stores acalendar database 252 that stores meeting event data 254 comprising dataassociated with at least one scheduled event. For example meeting eventdata 254 can comprise the contents of Table 1:

TABLE 1 Subject Patent Review Committee Meeting Date Feb. 1, 2012 StartTime 10:00 am End Time 11:00 am Dial In Number 204-555-1212 Log-In Code3459345

Table 1 comprises data associated with a meeting (i.e. a conferencecall) having a subject of “Patent Review Committee Meeting” scheduled onFeb. 1, 2012, starting at 10:00 am and ending at 11:00 am, that is to beheld via a conferencing server with dial-in number phone number“204-555-1212”, and with a participant code/log-in code of 3459345.While Table 1 is arranged in rows and columns, the format of Table 1and/or meeting event data 254 is appreciated to be generallynon-limiting. For example, while Table 1 includes rows and correspondingfields for a “Subject”, a “Date”, a “Start Time”, an “End Time”, a “DialIn Number” and a “Log-In Code”, the actual numbers of rows, columns,fields and format thereof, is appreciated to be non-limiting and Table 1can comprise more rows/fields or fewer rows/fields.

It is further appreciated that the log-in code comprises log-in data forjoining an associated conference call, the log-in data to be provided toa conference server once the conference server answers a call to theconference call server. In practice, once the conference server answersthe call, the log-in data is requested, for example by providing anindication to enter the log-in data (e.g. an audible indication such as“Please enter log-in data”). Log-in data is then entered at device 101and conveyed to the conference call server, for example via DTMF(dial-tone multi-frequency) signalling and the like.

It is further appreciated that while only one log-in code is depicted inTable 1, in other implementations, any suitable number of log-in codescan be provided, for example when an associated conference call requiresmore than one log-in code.

It is further appreciated that non-volatile storage can store at leastone template 255 for providing an indication of an incomingcommunication, for rendering at display 224 when an in-comingcommunication is received. For example, attention is directed to FIG. 2which depicts a non limiting example of template 255 which can bespecifically associated with telephone calls, including but not limitedto mobile calls, voice calls, VoIP calls, PSTN based calls, and thelike. As depicted, template 255 comprises text 279 indicative that an“Incoming Call” is being received, a field 280 for providing a pictureassociated with an incoming call, a field 282 for providing Caller ID(identification) associated with an incoming call, and an field 284 forproviding an identifier associated with an incoming call, such as anassociated telephone number and the like. Hence, when an incomingtelephone call is received, circuitry 230 is controlled at display 224to render representation 232 of template 255, with however fields 280,282, 284 populated with data associated with the incoming telephonecall. For example, field 282 is populated with the caller ID, and field284 is populated with the associated telephone number, each of which isreceived as metadata with the incoming telephone call. Field 280 can bepopulated either when image data is received with the incoming telephonecall and/or when image data associated with an identifier of theincoming call (e.g. the caller ID and/or the telephone number) is storedat non-volatile storage 212; otherwise field 280 can be left blank orpopulated with given generic image data, such as an outline of humanbeing, and the like. Such generic image data can be stored atnon-volatile storage 212 and/or field 280 can comprise such genericimage data, which would be substituted for image data associated withthe telephone call when present.

While template 255 has been described with reference to a telephonecall, it is appreciated that non-volatile storage 212 can store anysuitable number of similar templates for providing different types ofincoming communications. For example, templates for incoming textmessages, SMS (short message service) messages, MMS (multimedia messageservice) message, e-mail messages and the like can be provided.

In any event, it should be understood that in general a wide variety ofconfigurations for device 101 are contemplated.

Devices 105 can be similar to or different from device 101 and each ofdevices, 105 can include, but is not limited to, any suitablecombination of computing devices, personal computers, laptop computers,portable electronic devices, mobile computing device, portable computingdevices, tablet computing devices, laptop computing devices, PDAs(personal digital assistants), cellphones, smartphones and the like.Other suitable communication devices are within the scope of presentimplementations. Further, while two devices 105 are depicted in FIG. 1,it is appreciated that system 100 can comprise any suitable number ofcommunication devices. Devices 105 can comprise a processor, acommunication interface, volatile and non-volatile storage, an inputdevice, a display device, a microphone, and a speaker, similar to device101.

Device 103 is appreciated to also comprise a processor, non-volatilestorage, volatile storage, and a communication interface, however indepicted implementations device 103 comprises a server based on anywell-known server environment including a module that houses one or morecentral processing units, volatile memory (e.g. random access memory),persistent memory (e.g. hard disk devices) and network interfaces toallow device 103 to communicate over links 106, 108. For example, device103 can be a Sun Fire V480 running a UNIX operating system, from SunMicrosystems, Inc. of Palo Alto Calif., and having four centralprocessing units each operating at about nine-hundred megahertz andhaving about sixteen gigabytes of random access memory. However, it isto be emphasized that this particular server is merely exemplary, and avast array of other types of computing environments for device 103 arecontemplated. It is further more appreciated that device 103 cancomprise any suitable number of servers that can perform differentfunctionality of server implementations described herein.

Attention is now directed to FIG. 3 which depicts a method 300 forproviding an automatically initiated outgoing communication as anincoming communication, according to non-limiting implementations. Inorder to assist in the explanation of method 300, it will be assumedthat method 300 is performed using system 100. Furthermore, thefollowing discussion of method 300 will lead to a further understandingof system 100 and its various components. However, it is to beunderstood that system 100 and/or method 300 can be varied, and need notwork exactly as discussed herein in conjunction with each other, andthat such variations are within the scope of present implementations.

It is appreciated that, in some implementations, method 300 isimplemented in system 100 by processor 208 of device 101 processingapplication 250. Indeed, method 300 is one way in which device 101 canbe configured. It is to be emphasized, however, that method 300 need notbe performed in the exact sequence as shown; and likewise various blocksmay be performed in parallel rather than in sequence; hence the elementsof method 300 are referred to herein as “blocks” rather than “steps”. Itis also to be understood, however, that method 300 can be implemented onvariations of system 100 as well.

Furthermore, method 300 will be described with reference to FIGS. 4 and5, each of which are substantially similar to FIG. 1, with like elementshaving like numbers.

At block 301, an outgoing communication is automatically initiated at ascheduled given time. For example, processor 208 can determine that anoutgoing communication is at the scheduled given time by processingcalendar database 252 to determine that the outgoing communication isassociated with meeting data 254 associated with the scheduled giventime. With reference to Table 1 above, in a non-limiting example,processor 208 can determine that the outgoing communication with device103 is scheduled at 10:00 am on Feb. 1, 2012; hence, in this example,the scheduled given time is 10:00 am on Feb. 1, 2012. With reference toFIG. 4, processor 208 initiates an outgoing communication 401 withdevice 103 via interface 228 by automatically “dialling” the dial-innumber (e.g. with reference to Table 1, 204-555-1212) stored at meetingdata 254. Dialling is appreciated to mean any suitable steps and/ortransmission of data for setting up a communication with device 103, andis not meant to be limited to dialling of a telephone.

It is further appreciated, that block 301 can include: initiatingoutgoing communication 401; and, when a called communication device,such as device 103, responds to a request for initiating outgoingcommunication 401, automatically providing log-in data for joining aconference call to the called communication device. With reference toTable 1 above, in a non-limiting example, processor 208 can determinethat meeting data 254 comprises log-in data (e.g. with reference toTable 1, Log-In Code 3459345); hence, once outgoing communication 401 isinitiated, the log-in data, when present, can be provided to device 103(e.g. by using DTMF (dial-tone multi-frequency) signalling and the like,for example to join a conference call).

Furthermore, outgoing communication 401 can be automatically initiatedat one or more of the scheduled given time and within a given timeperiod before the scheduled given time. For example, with furtherreference to Table 1, outgoing communication 401 can be automaticallyinitiated at 10:00 am on Feb. 1, 2012 and/or within a given time periodbefore 10:00 am on Feb. 1, 2012, such as 5 minutes before the scheduledgiven time. However, the scheduling of outgoing communication 401 isgenerally considered to be non-limiting and outgoing communication 401can be scheduled at any suitable time.

Further, in some implementations, the scheduled time can beconfigurable, while in other implementations the scheduled time can beautomatically determined. For example, application 250 can be configuredto initiate communications at a scheduled given time stored atassociated meeting data stored in calendar database 252. Alternatively,application 250 can be configured to initiate communications a giventime period before a scheduled given time stored at associated meetingdata stored in calendar database 252. In yet further alternatives,respective scheduled given times can be configured for each set ofmeeting data stored at calendar database 252 associated with a telephonenumber and/or remote device identifier.

In yet further implementations, the scheduled time can be automaticallydetermined, for example via processor 208 processing associated meetingdata to determine whether log-in data, and the like, are to be providedwhen initiating an outgoing communication and determining the scheduledtime based on such. For example, threshold values can be set todetermine the scheduled given time: in some non-limitingimplementations, when the number of characters in the log-in data isbelow a threshold number of characters the scheduled time can be thescheduled given time, and when the number of characters in the log-indata is at or above a threshold number of characters, the scheduled timecan be at a time that is a given time period before the scheduled giventime.

Alternatively, when the number of log-in codes in the log-in data isbelow a threshold number of log-in codes, the scheduled time can be thescheduled given time, and when the number of log-in codes in the log-indata is at or above a threshold number of log-in codes, the scheduledtime can be at a time that is a given time period before the scheduledgiven time. In other words, processor 208 is enabled to estimate theamount of time needed to dial the log-in number and subsequently log-into the conference call.

Further, processor 208 can be enabled to provide log-in data after agiven time period following dialling the log-in number, and/or whenprompted by the called communication device.

Further, in some implementations, block 301 executes without providingany indication at device 101 that outgoing communication 401 is beinginitiated: for example, no dial-out indication is rendered at display224, no dial-out tones are provided at speaker 229, and when device 101comprises optional notification devices, such notification devices arenot activated. In other words, processor 208 suppresses notificationsassociated with out-going communications, and/or fails to initiate suchnotifications. Put another way, outgoing communication 401 is initiatedin the background.

In yet further implementations, outgoing communication 401 can beinitiated without providing an indicator of outgoing communication 401other than an indication rendered in an indicator area of display 224,including but not limited to an icon, a status icon, a radio-in-use iconand the like. The indicator area can comprise a header of representation232 at display 224.

In yet further implementations, at least a portion of normally providedindications outgoing communications are suppressed when outgoingcommunication 401 is initiated. For example, one or more of a dial-outindication and a dial-tone is suppressed. In some of theseimplementations, at least a portion of normally provided indications ofoutgoing communications are suppressed by muting speaker 229. Further,at least a portion of normally provided indications of outgoingcommunications can be suppressed by preventing rendering of anidentifier of a remote communication device associated with outgoingcommunication 401: for example, when outgoing communication 401 isintended for device 103, an identifier of device 103, for example atelephone number, is not rendered at display 224.

Rather, returning to FIG. 3, at block 303 after outgoing communication401 is initiated, an indication of outgoing communication 401 isprovided at device 101, such that outgoing communication 401 is providedas an incoming communication at device 401. In some implementations, anotification device at device 101 is activated to indicate that anincoming call can be accepted or declined: for example device 101 rings,vibrates, a light flashes, and/or a notification is rendered at display224.

Alternatively, template 255 can be populated and rendered at display224. For example, attention is again directed to FIG. 5 which depictsprocessor 208 processing meeting data 254 to populate fields 282, 284 oftemplate 255, and a representation of such is rendered in representation232 at display 224. A non-limiting example of representation 232 isdepicted in FIG. 6. From FIG. 6 it is appreciated that each of elements679, 680, 682, 684 of representation 232 corresponds to fields 279, 280,282, 284 of template 255. For example, element 679 comprises text“Incoming Call” similar to field 279. Element 680 corresponds to field280, however populated with generic image data as no incomingcommunication was actually received; rather an outgoing communicationwas initiated; in implementations where image data is stored atnon-volatile storage 212 in association with, for example, an identifierof device 103, processor 208 can populate filed 280 with such imagedata.

Element 682 corresponds to field 282, however populated with “Subject”data from Table 1. Similarly, element 684 corresponds to field 284,however populated with the “Dial-In Number” data from Table 1. Hence,“Subject” data of Table 1 is rendered as a caller ID in representation232 and “Dial-In Number” of Table 1 is rendered as an identifier ofdevice 103. In other words, an indication (e.g. representation 232) ofoutgoing communication 401 is provided as if outgoing communication 401were actually an incoming communication.

To this end, representation 232 further comprises virtual buttons 690,692 for respectfully accepting outgoing communication 401 or decliningoutgoing communication 40, as if outgoing communication 401 were anincoming call; each buttons 690, 692 can be actuated via input device200. In other words, device 101 provides representation 232 as anindication of outgoing communication 401, but as if outgoingcommunication 401 were actually an incoming communication and furtheruses the same template 255 used to provide indications of incomingcommunications. Buttons 690, 692 are appreciated to be only oneimplementation for accepting or declining outgoing communication 401,and that any suitable process and/or hardware for accepting or decliningoutgoing communication 401 is within the scope of presentimplementations.

It is appreciated that the indication of outgoing communication 401 isprovided as one or more of a caller ID, an identifier of outgoingcommunication 401, an identifier of a conference call associated withoutgoing communication 401, and an identifier of meeting data associatedwith the outgoing communication. Examples of various identifiersinclude, but are not limited to, a subject stored in associated meetingdata 254, start and end times associated with meeting data 254, anidentifier of device 103, such as a telephone number, log-in dataassociated with meeting data 254, some or all of which can be providedin fields 282, 284 of template 255, and the like.

In implementations where speaker 229 is muted at block 301, at block 303speaker is unmuted.

Various alternatives and variations of method 300 are within the scopeof present implementations.

For example, method 300 can further comprise, when connecting outgoingcommunication 401 is unsuccessful, automatically reattemptingautomatically initiating the outgoing communication 401 after a giventime period. For example, when outgoing communication 401 is notsuccessful at connecting with device 103, for example because device 103is busy and the like, block 301 can be re-executed after a suitablegiven time period (e.g. a few minutes). Block 301 can repeat untilcommunication 401 is successful. In other words, device 101 reattemptsto connect with device 101 if previous attempts to connect with device103 are unsuccessful. In some of these implementations, method 300 canend after a given number of executions of block 301 and/or after a giventime period.

In yet further implementations, no response to an indication of outgoingcommunication 401 can occur. In other words, when representation 292 ofFIG. 6 is provided at device 101, neither of buttons 690, 692 areactuated. Such a situation can be referred to as a “missed call”. Inthese implementations, a missed call log (not depicted) stored atnon-volatile storage 212 can be provided which stores a missed callentry associated with communication 401. For example, a missed callentry could include, but is not limited to, data provided at one or moreof elements 682, 684, along with additional context data indicating acontext of associated communication 401. For example, the call log entrycould comprise one or more icons indicating that the missedcommunication 401 was an outgoing call, a conference call or the like.As a further example, when communication 401 is associated with areminder, such as a birthday reminder, the icon could comprise a pictureassociated with the reminder: when a birthday reminder, the icon couldcomprise a birthday cake, etc.

In any event, storing of context information associated withcommunication 401 in the missed call entry could enable missed call logto processed and/or accessed in the context of communication 401. At aminimum, such context information could indicate to a user of device 101the nature of communication 401 when the missed call entry is renderedat display 224 along with the context information.

In some of these implementations, the missed call entry can compriseadditional options based on context when rendered at display 224. Forexample, when communication 401 was missed and communication 401comprised a conference call, when the associated missed call entry isrendered at display 224, options related to conference calls can beprovided as virtual buttons, including but not limited to “JoinConference”, “Join Conference Silently”, “Join Conference as Moderator”,and the like; when a virtual buttons are actuated, the indicated actionbe taken at device 101.

Indeed, in yet further implementations, the indication (e.g.representation 232) of outgoing communication 401 can be provided whenone of a called communication device (e.g. device 103) answers outgoingcommunication 401 (e.g. the call to device 103 is answered), and whenoutgoing communication 401 is logged into an associated conference call.For example, processor 208 can be enabled to render the indication (e.g.representations 232) of outgoing communication when device 103 answersoutgoing communication 403, such that when accept button 690 isactuated, device 103 is connected and, other then entering the log-indata (which can be done either manually or automatically), device 103 isconnected to device 101, and a user of device 101 can start speaking inthe conference call. Similarly, the indication (e.g. representation 232)of outgoing communication 401 can be provided when outgoingcommunication 401 is logged into an associated conference call such thatupon actuation of button 690, a user of device 101 can start speaking inthe conference call.

However, providing the indication of outgoing communication 401 can beprovided before a called communication device (e.g. device 103) answersoutgoing communication 401. In these implementations, when button 690 isactuated, “ringing” or any other suitable notification is played atspeaker 229 to indicate that the called communication device (e.g.device 103) has not yet accepted outgoing communication 401.Alternatively, when the indication is provided before one of a calledcommunication device (e.g. device 103) answers the outgoingcommunication 401 and the outgoing communication 401 is logged into anassociated conference call, the outgoing communication 401 can be muteduntil, for example the outgoing communication 401 is answered and/or theconference call is entered.

While present implementations have been described with reference todialling into a conference call at a conference call server, it isappreciated that method 300 is not so limited. Rather, method 300 can beimplemented at device 101 to provide an automatically initiated outgoingcommunication to any suitable communication device as an incomingcommunication, for example one or more of devices 105. Further, method300 can be implemented sequentially to set up conference calls. Forexample, when meeting data 254 comprises more than one phone number,each number can be dialled in any suitable sequence, in the background(i.e. block 301 executes more than once, and/or one time for each phonenumber), and block 303 executes at a suitable time, for example onceeach phone number is connected.

Furthermore, method 300 is not limited to phone calls. Rather, anyoutgoing communication can be provided at device 101 as an incomingcommunication. For example, device 101 can automatically initiate a textmessage session and provide an outgoing text message as an incoming textmessage. As a further example, device 101 can automatically initiate avideo call and provide an outgoing video call as an incoming video call.

In any event, providing an automatically initiated outgoingcommunication as an incoming communication, a convenient method ofautomatically setting up communications between devices is provided, aswell as a convenient method of ensuring that scheduled meetingsconducted via communication devices is attended.

Those skilled in the art will appreciate that in some implementations,the functionality of device 101 can be implemented using pre-programmedhardware or firmware elements (e.g., application specific integratedcircuits (ASICs), electrically erasable programmable read-only memories(EEPROMs), etc.), or other related components. In other implementations,the functionality of devices 101 can be achieved using a computingapparatus that has access to a code memory (not shown) which storescomputer-readable program code for operation of the computing apparatus.The computer-readable program code could be stored on a computerreadable storage medium which is fixed, tangible and readable directlyby these components, (e.g., removable diskette, CD-ROM, ROM, fixed disk,USB drive). Furthermore, it is appreciated that the computer-readableprogram can be stored as a computer program product comprising acomputer usable medium. Further, a persistent storage device cancomprise the computer readable program code. It is yet furtherappreciated that the computer-readable program code and/or computerusable medium can comprise a non-transitory computer-readable programcode and/or non-transitory computer usable medium. Alternatively, thecomputer-readable program code could be stored remotely buttransmittable to these components via a modem or other interface deviceconnected to a network (including, without limitation, the Internet)over a transmission medium. The transmission medium can be either anon-mobile medium (e.g., optical and/or digital and/or analogcommunications lines) or a mobile medium (e.g., microwave, infrared,free-space optical or other transmission schemes) or a combinationthereof.

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by any one of the patentdocument or patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightswhatsoever.

Persons skilled in the art will appreciate that there are yet morealternative implementations and modifications possible, and that theabove examples are only illustrations of one or more implementations.The scope, therefore, is only to be limited by the claims appendedhereto.

What is claimed is:
 1. A communication device comprising: a processorand a communication interface, the processor enabled to: automaticallyinitiate an outgoing communication at a scheduled given time via thecommunication interface; and, after the outgoing communication isinitiated, provide an indication of the outgoing communication, suchthat the outgoing communication is provided as an incomingcommunication.
 2. The communication device of claim 1, wherein theindication of the outgoing communication is provided as one or more of acaller ID (identification), an identifier of the outgoing communication,an identifier of a conference call associated with the outgoingcommunication, and an identifier of meeting data associated with theoutgoing communication.
 3. The communication device of claim 1, whereinthe indication comprises an incoming communication template with fieldspopulated with outgoing communication data.
 4. The communication deviceof claim 1, wherein the processor is further enabled to determine thatthe outgoing communication is scheduled by processing a calendardatabase to determine that the outgoing communication is associated withmeeting data associated with the scheduled given time.
 5. Thecommunication device of claim 1, wherein the processor is furtherenabled to automatically initiate the outgoing communication at one ormore of the scheduled given time and within a given time period beforethe scheduled given time.
 6. The communication device of claim 1,wherein the processor is further enabled to automatically initiate theoutgoing communication by: initiating the outgoing communication; and,when a called communication device responds to a request for initiatingthe outgoing communication, automatically providing log-in data forjoining a conference call to the called communication device.
 7. Thecommunication device of claim 1, wherein the processor is furtherenabled to, when connecting the outgoing communication is unsuccessful,automatically reattempt to automatically initiate the outgoingcommunication after a given time period.
 8. The communication device ofclaim 1, wherein the processor is further enabled to provide theindication of the outgoing communication when one of a calledcommunication device answers the outgoing communication, and when theoutgoing communication is logged into an associated conference call. 9.The communication device of claim 1, wherein the processor is furtherenabled to, when the indication is provided before one of a calledcommunication device answers the outgoing communication and the outgoingcommunication is logged into an associated conference call, mute theoutgoing communication.
 10. A method comprising: automaticallyinitiating, at a processor of a communication device, an outgoingcommunication at a scheduled given time via a communication interface ofthe communication device; and, after the outgoing communication isinitiated, providing an indication of the outgoing communication at thecommunication device, such that the outgoing communication is providedas an incoming communication at the communication device.
 11. The methodof claim 10, wherein the indication of the outgoing communication isprovided as one or more of a caller ID (identification), an identifierof the outgoing communication, an identifier of a conference callassociated with the outgoing communication, and an identifier of meetingdata associated with the outgoing communication.
 12. The method of claim10, wherein the indication comprises an incoming communication templatewith fields populated with outgoing communication data.
 13. The methodof claim 10, further comprising determining that the outgoingcommunication is scheduled by processing a calendar database todetermine that the outgoing communication is associated with meetingdata associated with the scheduled given time.
 14. The method of claim10, wherein the outgoing communication is automatically initiated at oneor more of the scheduled given time and within a given time periodbefore the scheduled given time.
 15. The method of claim 10, wherein theautomatically initiating the outgoing communication comprises:initiating the outgoing communication; and, when a called communicationdevice responds to a request for initiating the outgoing communication,automatically providing log-in data for joining a conference call to thecalled communication device.
 16. The method of claim 10, furthercomprising, when connecting the outgoing communication is unsuccessful,automatically reattempting automatically initiating the outgoingcommunication after a given time period.
 17. The method of claim 10,wherein the indication of the outgoing communication is provided whenone of a called communication device answers the outgoing communication,and when the outgoing communication is logged into an associatedconference call.
 18. The method of claim 10, wherein when the indicationis provided before one of a called communication device answers theoutgoing communication and the outgoing communication is logged into anassociated conference call, the outgoing communication is muted.
 19. Anon-transitory computer program product, comprising a computer usablemedium having a computer readable program code adapted to be execute amethod comprising: automatically initiating, at a processor of acommunication device, an outgoing communication at a scheduled giventime via a communication interface of the communication device, theoutgoing communication initiated without providing an indicator of theoutgoing communication at the communication device; and, after theoutgoing communication is initiated, providing an indication of theoutgoing communication at the communication device, such that theoutgoing communication is provided as an incoming communication at thecommunication device.